Intelligent generation of log messages by a SaaS offering in a continuous pipeline

ABSTRACT

An adaptive log system and method may include calculating a complexity of the change set, comparing a current log message with a previous log message created as a result of the test operation during a previous run, to determine a log difference between the current log message and the previous log message, determining a module sensitivity for each module of the change set, identifying a trust level of a developer of the change set, dynamically adjusting log level settings, and analyzing a serviceability of the change set made to the continuous delivery pipeline based on: (i) the complexity of the change set, (ii) the log difference, (iii) the module sensitivity of each module of the change set, and (iv) the trust level of the developer, wherein, as a function of the analyzing, the sufficiency of log messages for each module of the change set is determined.

TECHNICAL FIELD

The present invention relates to systems and methods for log messagegeneration, and more specifically the embodiments of an adaptive logsystem for providing feedback to developers of a sufficiency of logmessages associated with the changes made to computer program (or sourcecode) of a SaaS product delivered using a continuous delivery pipelinein a SaaS environment.

BACKGROUND

DevOps teams for SaaS environments continuously deliver new features ata rapid pace. A continuous delivery process and tool enables DevOpsengineers to continuously fix defects and release new features tostaging and eventually to production. The SaaS operation team needs tobe in-sync with the changes that are being introduced in the DevOpspipeline, so that the SaaS operation team can closely monitor the systemfor any new defect, rapidly isolate problems and resolve the problemswith the help from a Development engineer. For instance, SaaS Operationsengineers typically depend on log messages generated by the SaaSenvironment to isolate and resolve issues.

SUMMARY

An aspect of this invention relates to a method, computer system, andcomputer program product for providing feedback to developers of asufficiency of log messages associated with a change set made tocomputer program (or source code) of a SaaS product delivered using acontinuous delivery pipeline in a SaaS environment. A processor of acomputing system calculates a complexity of the change set made to theSaaS product. A current sequence of log messages created as a result ofa test operation of the continuous delivery pipeline during a currentrun is compared with a previous sequence of log messages created as aresult of the test operation during a previous run, to determine changesin the log message or existence of new log messages in the source code.A module sensitivity for each module of the change set is determined. Atrust level of a developer of the change set is identified. Aserviceability of the change set made to the continuous deliverypipeline is analyzed based on: (i) the complexity of the change set,(ii) the log difference, (iii) the module sensitivity of each module ofthe change set, and (iv) the trust level of the developer, wherein, as afunction of the analyzing, the sufficiency of log messages for eachmodule of the change set is determined.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram of an adaptive log system, in accordancewith embodiments of the present invention.

FIG. 2 depicts a schematic view of the adaptive log system, with acontinuous delivery pipeline and a computing system, in accordance withembodiments of the present invention.

FIG. 3 depicts a flow chart diagram of several inputs used by thecomputing system, in accordance with embodiments of the presentinvention.

FIG. 4 depicts a log sufficiency recommendation table, in accordancewith embodiments of the present invention.

FIG. 5 depicts a flow diagram of a change stability factor used forcomputing log level settings, in accordance with embodiments of thepresent invention.

FIG. 6 depicts a graphical illustration of change stability calculatedover time based on a number of problems occurring with the change setand an effect on an initial log level over time, in accordance withembodiments of the present invention.

FIG. 7 depicts a flow chart of a method for providing feedback todevelopers of a sufficiency of log messages associated with a change setmade to a continuous delivery pipeline in a SaaS environment, inaccordance with embodiments of the present invention.

FIG. 8 depicts a flow chart of a method for dynamically configuring loglevels, in accordance with embodiments of the present invention.

FIG. 9 depicts a block diagram of a computer system for the adaptive logsystem 100 of FIGS. 1-6, capable of implementing methods for providingfeedback to developers of a sufficiency of log messages associated witha change set made to a continuous delivery pipeline in a SaaSenvironment of FIG. 7, and for dynamically configuring log levels inFIG. 8, in accordance with embodiments of the present invention.

FIG. 10 depicts a cloud computing environment, in accordance withembodiments of the present invention.

FIG. 11 depicts abstraction model layers, in accordance with embodimentsof the present invention.

DETAILED DESCRIPTION

A SaaS operation team must be in-sync with the changes that are beingintroduced in the DevOps pipeline, so that the SaaS operation team canclosely monitor the system for any new defect, rapidly isolate problemsand resolve the problems, with help from a development team member. ASaaS Operations engineer is typically dependent on logs generated by theSaaS environment (e.g. application/infrastructure) to isolate & resolveissues. The SaaS Operations team can adjust log level settings (e.g.Debug, Info, Trace, Error, Warning, etc.) based on a risk perception andtrade-off with an overall performance of the SaaS application. However,the SaaS Operations engineer can be faced with a limitation ofdiscretely and manually tuning a logging system to emit logs from thedifferent modules of the SaaS system. In addition, the SaaS Operationsteam may be expected to follow the long drawn change management processto introduce changes in the production system. When the SaaS Developmentand Operations team (DevOps) are out-of-sync, the DevOps team can befaced with insufficient logs from the SaaS environment to debug aproblem. Thus, there is a need to configure the logging system tooptimally emit logs, and for the DevOps team to be in-sync with thechanges being introduced in the continuous delivery pipeline, throughsufficient log messages created in the SaaS environment. In addition,the adaptive log system can dynamically control the nature of (or, classof) log message generated by the individual internal module of a runningSaaS product, based on the stability of the changes that were recentlyintroduced into the SaaS product.

Embodiments of the present invention may relate to a method, computersystem, and computer program that can dynamically control the class oflog message generated by the individual internal modules of a runningSaaS product, based on the changes that were recently introduced intothe SaaS product. Wherein, the log message is typically classified asfatal, error, major, minor, info or debug; and the log level settingsdetermine the class of log messages that will be emitted by the internalcomponents of the SaaS product. The log message generation isdynamically controlled based on the stability of recent change made tothe SaaS product. The change-stability is computed for all the modulesof the SaaS product, based on i) the complexity and recency of thechange set, wherein the complexity of change set can influence adjustinglog level settings based on severity/priority of the defect, number offiles changed, result of static code analysis, code coverage analysis,KLOC delivered as a part of change etc.; (ii) the module sensitivity ofeach module of the change set, wherein the module sensitivity can alsoinfluence adjusting log level settings based on a percentage of highseverity defects addressed in that module/file, historical informationabout the frequency of changes made in this module/file, type of fileand how many times regressions reported again the same module/file etc.;(iii) the trust level of the developer, wherein the trust level of theDevOps person can be measured based on complexity handled, problemsreported from the field related to the changes delivered, time spent inthe same project, quality of the code delivered, critical defects fixed,defects re-opened etc.; and/or (iv) the number of problems reported bythe users against the module of SaaS product, and the age of theproblem, also affects the risk of failure in all the modules of the SaaSproduct. The change-stability computation function uses all theseparameters and periodically computes the change-stability factor. Thechange-stability factor is used to dynamically determine the log levelsettings for the modules of the SaaS product.

Referring to the drawings, FIG. 1 depicts a block diagram of an adaptivelog system 100, in accordance with embodiments of the present invention.Embodiments of the adaptive log system 100 may be a system for providingfeedback to developers of a sufficiency of log messages associated witha change set made to a continuous delivery pipeline in a SaaSenvironment 111. Embodiments of the adaptive log system 100 may beuseful for SaaS DevOps teams for improving defects, problems, issues,etc. that may occur within the SaaS environment 111. For example, theadaptive log system 100 may intelligently provide feedback to adevelopment SaaS team member about insufficient log messages for changesintroduced into the SaaS offerings based on a change complexity and amodule sensitivity of a change set. Further, embodiments of the adaptivelog system 100 may dynamically set a log level based on prior problemsand defects, change complexity, and module sensitivity to ensuresufficient logs for highly sensitive changes. Embodiments of theadaptive log system 100 may continuously change the log level settingbased on the continuous learning from the field (e.g. new problemsoccurring in the continuous delivery pipeline) to ensure sufficient logsto support further problem determination.

Embodiments of the adaptive log system 100 may be an adaptive logcontroller system, a log message system, a log message serviceabilitydetermination system, a SaaS quality control system, a dynamic log levelsystem, a log level tuning system, and the like. Embodiments of theadaptive log system 100 may include a computing system 120. Embodimentsof the computing system 120 may be a computer system, a computer, aserver, one or more servers, an adaptive log controller, and the like.

Furthermore, embodiments of adaptive log system 100 may include acontinuous delivery pipeline 110 of a SaaS environment 111 that iscommunicatively coupled to a computing system 120 of the adaptive logsystem 100 over a computer network 107. For instance, information/datamay be transmitted to and/or received from the continuous deliverypipeline 110 over a network 107. A network 107 may be the cloud. Furtherembodiments of network 107 may refer to a group of two or more computersystems linked together. Network 107 may be any type of computer networkknown by individuals skilled in the art. Examples of network 107 mayinclude a LAN, WAN, campus area networks (CAN), home area networks(HAN), metropolitan area networks (MAN), an enterprise network, cloudcomputing network (either physical or virtual) e.g. the Internet, acellular communication network such as GSM or CDMA network or a mobilecommunications data network. The architecture of the network 107 may bea peer-to-peer network in some embodiments, wherein in otherembodiments, the network 107 may be organized as a client/serverarchitecture.

In some embodiments, the network 107 may further comprise, in additionto the computing system 120, a connection to one or morenetwork-accessible knowledge bases 114, which are network repositoriescontaining SaaS environment data, network repositories or other systemsconnected to the network 107 that may be considered nodes of the network107. In some embodiments, where the computing system 120 or networkrepositories allocate resources to be used by the other nodes of thecomputer network 107, the computing system 120 and network-accessibleknowledge bases 114 may be referred to as servers.

The network-accessible knowledge bases 114 may be a data collection areaon the computer network 107 which may back up and save all the datatransmitted back and forth between the nodes of the computer network107. For example, the network repository may be a data center saving andcataloging SaaS development and operations data, to generate bothhistorical and predictive reports regarding a particular SaaSenvironment. In some embodiments, a data collection center housing thenetwork-accessible knowledge bases 114 may include an analytic modulecapable of analyzing each piece of data being stored by thenetwork-accessible knowledge bases 114. Further, the computing system120 may be integrated with or as a part of the data collection centerhousing the network-accessible knowledge bases 114. In some alternativeembodiments, the network-accessible knowledge bases 114 may be a localrepository that is connected to the computing system 120.

FIG. 2 depicts a schematic view of the adaptive log system 100, with acontinuous delivery pipeline 110 and a computing system 120, inaccordance with embodiments of the present invention. Embodiments of thecontinuous delivery pipeline 110 may be a continuous delivery pipeline,a continuous integration and continuous delivery pipeline, a deploymentpipeline, a pipeline that automatically tests and deploys software codeas part of a SaaS application/infrastructure, and the like. Embodimentsof the pipeline 110 may include aspects of a SaaS developmentteam/engineer and a SaaS operations team/engineer. The pipeline 110 mayflow in both directions, and may include a plurality of components. Forexample, the pipeline 110 may include a source control component, abuild and test component, a code analysis component, a deploy to testenvironment component, an integration test component, a deploy tostaging component, an acceptance test component, a deploy to productioncomponent, and a monitor and manage component. Other embodiments ofpipeline 110 may include additional components, or may include lesscomponents than shown in FIG. 2. At various point in the continuousdelivery pipeline, information/data may be communicated to the computingsystem 120. As described in greater detail infra, the computing system120 may receive data associated with the change set, modules and filesinformation of the change set, developer identification information, logmessages from the change set or regarding the change set, usage metrics,and the like. The computing system 120 may then provide feedback to aSaaS development team to improve serviceability of one or more logscreated during test operations of the pipeline 110, as well asdynamically configure log level settings that may be tuned or otherwisefiltered by the SaaS operations teams when addressing problems associatewith the SaaS environment 111. Accordingly, the pipeline 110 maytransmit, initiate, create, send, etc. (e.g. over a network 107)discrete data inputs and information to computing system 120.Embodiments of the device 110 may connect to the computing system 120over network 107. The pipeline 110 may be running one or more softwareapplications and tools communicating with computing system 120.

Referring back to FIG. 1, embodiments of the computing system 120 may beequipped with a memory device 142 which may store variousdata/information/code, and a processor 141 for implementing the tasksassociated with the adaptive log system 100. In some embodiments, anadaptive log application 130 may be loaded in the memory device 142 ofthe computing system 120. The computing system 120 may further includean operating system, which can be a computer program for controlling anoperation of the computing system 120, wherein applications loaded ontothe computing system 120 may run on top of the operating system toprovide various functions. Furthermore, embodiments of computing system120 may include the adaptive log application 130. Embodiments of theadaptive log application 130 may be an interface, an application, aprogram, a module, or a combination of modules. In an exemplaryembodiment, the adaptive log application 130 may be a softwareapplication running on one or more back end servers, such as computingsystem 120.

The adaptive log application 130 of the computing system 120 may includea complexity module 131, a comparing module 132, a sensitivity module133, a trust level module 134, an analytics module 135, and a tuningmodule 136. A “module” may refer to a hardware-based module,software-based module or a module may be a combination of hardware andsoftware. Embodiments of hardware-based modules may includeself-contained components such as chipsets, specialized circuitry andone or more memory devices, while a software-based module may be part ofa program code or linked to the program code containing specificprogrammed instructions, which may be loaded in the memory device of thecomputing system 120. A module (whether hardware, software, or acombination thereof) may be designed to implement or execute one or moreparticular functions or routines.

Embodiments of the complexity module 131 may include one or morecomponents of hardware and/or software program code for calculating acomplexity of the change set made to the continuous delivery pipeline. Achange set may be a change, such as new code, entered into thecontinuous delivery pipeline to effectuate a change or addition to theSaaS application and/or infrastructure. Each change set may include aplurality of modules. The complexity module 131 may calculate,determine, analyze, etc. a complexity or a complexity value/level of thechange set uploaded to the continuous delivery pipeline 110. FIG. 3depicts a flow chart diagram of several inputs used by the computingsystem 120, in accordance with embodiments of the present invention.Embodiments of the complexity module 131 may calculate the complexity ofthe change set output 200 by implementing one or more of the followingsteps 201-06. At step 201, the complexity module 131 of the computingsystem 120 may identify the modules related to the change set. Thechange set may be transmitted to the computing system 120 from thecontinuous delivery pipeline. At step 202, the complexity module mayidentify the developers involved in the change set. For instance, thecomplexity module 131 may obtain an identity of a developer via adeveloper identification number associated with the change set. At step203, the complexity module 131 may identify a type of file that waschanged. Problems or defects related to certain types of files beingchanged are more difficult and complex to resolve, which can influencethe overall complexity. At step 204, the complexity module 131 mayidentify a volume of change, such as KLOC and/or a number of filed beingchanged or affected by the change set. For example, the complexitymodule 131 may analyze the total number of lines of code included in thechange set, as well as the number of separate files that have beenaffected to consider volume of a change within the change set. At step205, the complexity module may identify a number of work items and arecency of changes with the change set. A more recent change mayindicate that the solution to a potential defect may be more complexbecause an operations team may not yet have encountered the problem, orthe change has to do with new features, which can add to the complexity.At step 206, the complexity module 131 may calculate the changecomplexity using the data/information gathered in steps 201-206. Eachfactor/data/information/input may be considered at equal weights or aweighting scheme may be applied to determine a complexity of the changeset. The complexity output 200 may be a value, a number, a score, andthe like, which may be used for later calculations by computing system120 to determine a serviceability of the change set as well as used todynamically configured a logging system, as described in greater detailinfra.

Referring back to FIG. 1, embodiments of the computing system 120 mayfurther include a comparing module 132. Embodiments of the comparingmodule 132 may include one or more components of hardware and/orsoftware program for comparing a current log message created as a resultof a test operation of the continuous delivery pipeline 110 during acurrent run with a previous log message created as a result of the testoperation during a previous run, to determine a log difference betweenthe current log message and the previous log message. For instance, alog difference may be the result of log message comparison from previousruns, wherein a greater log difference may indicate that new content iscontained within the log messages, and a sufficiency of the log messagesmay be increased. A low or zero log difference may mean that no contenthas been added in the most current log message from the previous run,which could indicate that there is a lack of needed content in thecurrent log message for SaaS operations to address any problemsassociated with the change set. Log messages may be created after achange set is tested at various points in the continuous deliverypipeline 110.

With reference again to FIG. 3, embodiments of the comparing module 132may compare a current log message with a log message(s) from a previousrun to determine a log difference output 210 by implementing one or moreof the following steps 211-213. At step 211, the comparing module 132may, as a result of the comparison, identify a test case identificationof a particular test operation conducted within the continuous deliverypipeline 110, involved in validating the module. At step 212, thecomparing module 132 may, as a result of the comparing, extract relevantlog messages from the modules of the change set from a previous run(e.g. the last run). The data from the historical log messages may beretrieved or otherwise received from a database storing historical logmessages, and may be sorted or retrievable by test identificationnumber. At step 213, the comparing module 132 may compute the logdifference output 210 using the information/data from steps 211-212.

With continued reference to FIGS. 1 and 3, embodiments of the computingsystem 120 may include a sensitivity module 133. Embodiments of thesensitivity module 133 may include one or more components of hardwareand/or software program for determining a module sensitivity for eachmodule of the change set. The module sensitivity may be calculated foreach module of the change set, or a portion of modules of the change setdetermined to be the most relevant or important modules of the changeset. Embodiments of the sensitivity module 133 of the computing system120 may have access to a defect/problem history of the continuousdelivery pipeline 110, as well as a repository storing code providedwithin the continuous delivery pipeline. Embodiments of the sensitivitymodule 133 may determine a module sensitivity output 220 by implementingone or more steps 221-224. At step 221, embodiments of the sensitivitymodule 133 may extract information about a defect and a field problemhistory. At step 222, the sensitivity module 133 may extract a number ofdevelopers that contributed to the module(s). At step 223, thesensitivity module 133 may determine, calculate, compute, or otherwiseascertain a module complexity for each module, which may be based on anumber of files, a size of the files, cross-references, and the like. Atstep 224, the sensitivity module 133 may compute the module sensitivityoutput 220 using the information/data from steps 221-223.

Embodiments of the computing system 120 may also include a trust levelmodule 134. Embodiments of the trust level module 134 may include one ormore components of hardware and/or software program code for identifyinga trust level of a developer of the change set. For instance, the trustlevel of the developer may influence a serviceability recommendationmade by the computing system 120. Embodiments of the trust level module134 may determine a developer trust level output 230 by implementing oneor more steps 231-233. At step 231, embodiments of the trust levelmodule 134 may extract a contribution of a developer and a duration orexperience level of the developer associated with the change set. Atstep 232, the trust level module 134 may extract a number of issuesreporting in the past against a particular developer. At step 223, thetrust level module 134 may compute the developer trust level output 230using the information/data from steps 231-232.

Referring still to FIGS. 1 and 3, embodiments of the computing system120 may include an analytics module 135. Embodiments of the analyticsmodule 135 may include one or more components of hardware and/orsoftware program for analyzing a serviceability of the change set madeto the continuous delivery pipeline 110. The analytics module 135 maydetermine a serviceability (e.g. serviceability output 240) of thechange set based on: (i) the complexity of the change set output 200,(ii) the log difference output 210, (iii) the module sensitivity output220 of each module of the change set, and (iv) the trust level of thedeveloper output 230. The outputs 200, 210, 220, 230 may be used by theanalytics modules 135 to, as a function of the analyzing, determine asufficiency of log messages for each module of the change set. If theanalytics module 135 determines that a particular change set wouldresult in insufficient log messages, then the analytics module 135 ofthe computing system 120 may reject, delete, remove, etc, or otherwisedeal with the code associated with the change set within the continuousdelivery pipeline 110. If the analytics module 135 of the computingsystem 120 determines that the change set would result in sufficient logmessages, the analytics module 135 may accept the new code associatedwith the change set. Furthermore, the analytics module 135 may recommenda sufficiency of the log messages for serviceability for each module,based on the outputs 200, 210, 220, 230. FIG. 4 depicts a logsufficiency recommendation table 250, in accordance with embodiments ofthe present invention. The table 250 may include outputs from thecomputing system 120 regarding a serviceability of the change set. Thetable 250 may include the outputs 200, 210, 220, 230, and the outputrecommendation in columns, with various change sets in the rowdirection. For example, a first change set in a top row may have a high(H) module complexity, a high (H) change set complexity, a low (L) logdifference, and a medium (M) trust level in the developer. Thus, theanalytics module 120 of the computing system 120 may determine that theoutput recommendation of the serviceability of the first change set maybe poor. In contrast, a second change set in the middle row may have alow (L) module complexity, a low (L) change set complexity, a low (H)log difference, and a medium (M) trust level in the developer. Thus, theanalytics module 120 of the computing system 120 may determine that theoutput recommendation of the serviceability of the second change set maybe strong. A third change set in the bottom row of table 250 may a havemedium (M) module complexity, a medium (M) change set complexity, amedium (M) log difference, and a medium (M) trust level in thedeveloper. Thus, the analytics module 120 of the computing system 120may determine that the output recommendation of the serviceability ofthe third change set may be fair. The results in the table 250 may beconfigurable and manipulated by a member of a DevOps team.

Referring back to FIG. 1, embodiments of the computing system 120 mayalso include a tuning module 135. Embodiments of the tuning module 135may include one or more components of hardware and/or software programcode for determining a log level for each module of the change set. Thetuning module 136 may determine a log level output 270. Thedetermination of a log level output 270 may be based on outputs 200,210, 220, 230, in particular, on (i) the complexity of the change set,(ii) the log difference, (iii) the module sensitivity of each module ofthe change set, and (iv) the trust level of the developer. FIG. 5depicts a flow diagram of a change stability factor used for computinglog level settings, in accordance with embodiments of the presentinvention. Embodiments of the tuning module 136 may also apply astability factor 260 of the change set modules to assist in determininga configurable dynamic log level setting and tuning system. For example,the log level determination may be further based on a change stabilityfactor 260, determined by implementing one or more steps 261-263. Atstep 261, the tuning module 136 of the computing system 120 maydetermine whether a change in a log level of a change set over time. Atstep 262, the tuning module 136 may determine whether any problems havebeen reported in a past ‘x’ amount of time (e.g. hours). At step 263,the tuning module 136 may determine the stability factor from thedata/information obtained in steps 261-262. FIG. 6 depicts a graphicalillustration 265 of change stability calculated over time based on anumber of problems occurring with the change set and an effect on aninitial log level over time, in accordance with embodiments of thepresent invention. Log levels may include high (H), which may recordfatals, errors, warnings, info, and debug, medium (M), which may recordfatals, errors, and warnings, and default (D), which may record errors.An example change set having an identification number “5677” may have aninitial log level of high (H), and after a certain time, at t1, the loglevel remains at high (H), with 10 problem records (pr) against thechange set, at t2, the log level remains high (H) with the same 10problem records (pr) against the change set, and t3, the log level hasbeen changed to medium (M) with 10 problem records (pr) against thechange set. In this example, change set 5677 has log level changes fromaggressive to moderate. In another example, change set having anidentification number “5673” may have an initial log level of medium(M), and after a certain time, at t1, the log level remains at medium(H), with 0 problem records (pr) against the change set, at t2, the loglevel has changed to default (D) with zero problem records (pr) againstthe change set, and t3, the log level remains at default (D) with 00problem records (pr) against the change set. In this example, change set5673 has log level changes from moderate/medium to default. In yetanother example in FIG. 6, change set having an identification number“5443” may have an initial log level of default (D), and after a certaintime, at t1, the log level remains at default (H), with 5 problemrecords (pr) against the change set, at t2, the log level has changed tomedium (M) now with 12 problem records (pr) against the change set, andt3, the log level has been changed to high (H) now with 18 problemrecords (pr) against the change set. In this example, change set 5443has log level changes from default to aggressive.

Accordingly, a stability factor 260 may be calculated by the tuningmodule 136 for application to the log setting/tuning output 270, shownin FIG. 5. The output 270 may compute the log level setting for eachmodule of the change set based on outputs outputs 200, 210, 220, 230 asdescribed above, as well as with the stability factor 260. The log leveloutput 270 may be used by the computing system 120 to create log leveltable 280, which may display/indicate a log level setting for eachmodule of the of the change set based on the outputs 200, 210, 220, 230,240, 260. The table 280 shows a change complexity, a module sensitivity,trust level, a change stability, and an output log level in the columnsof the table. A first change set in the top row may have a changecomplexity of high (H), a module sensitivity of medium/moderate (M), atrust level of high (H), and a change stability of moderate (M), and sothe tuning module 136 of the computing system 120 may determine anoutput log level for the first change set to be high (H). A secondchange set in the bottom row of table 280 may have a change complexityof low (L), a module sensitivity of medium/moderate (M), a trust levelof medium (M), and a change stability of high (H), and so the tuningmodule 136 of the computing system 120 may determine an output log levelfor the second change set to be default (D).

Furthermore, the log level for each module of the change set may bedynamically configured to return log messages of the continuous deliverypipeline for a specific log level. For instance, embodiments of thetuning module 136 of the computing system 120 may filter, configure,sort, generate, etc. the determined log levels in response to a requestby a DevOps engineer to display a log level setting table, similar totable 280, but with only change sets in a specific, request log level.For example, a user may request to see change sets, and log messagesthereof, for change sets having a high (H) log level. In this way, theuser may be able to only see high log level change sets, which mayrecord fatal, errors, warnings, debugs, and info. Therefore, embodimentsof the computing system 120 may provide a dynamic configurable loggingsystem associated with a SaaS environment.

Various tasks and specific functions of the modules of the computingsystem 120 may be performed by additional modules, or may be combinedinto other module(s) to reduce the number of modules. Further,embodiments of the computer or computer system 120 may comprisespecialized, non-generic hardware and circuitry (i.e., specializeddiscrete non-generic analog, digital, and logic-based circuitry)(independently or in combination) particularized for executing onlymethods of the present invention. The specialized discrete non-genericanalog, digital, and logic-based circuitry may include proprietaryspecially designed components (e.g., a specialized integrated circuit,such as for example an Application Specific Integrated Circuit (ASIC),designed for only implementing methods of the present invention).Moreover, embodiments of the adaptive log system 100 offers a technicalimprovement over the existing art using a method for providing feedbackto developers of a sufficiency of log messages associated with a changeset made to a continuous delivery pipeline in a SaaS environment. Thetechnical improvement of the adaptive log system 100 improves softwaredebugging, technical problem resolution in a continuous deliverypipeline that prior to the adaptive log system 100, was hindered byinsufficient log message generation from the continuous deliverypipeline. Further, the adaptive log system 100 may be individualized toeach change set and to each SaaS application/infrastructure.

Referring now to FIG. 7, which depicts a flow chart of a method 300 forproviding feedback to developers of a sufficiency of log messagesassociated with a change set made to a continuous delivery pipeline in aSaaS environment, in accordance with embodiments of the presentinvention. One embodiment of a method 300 or algorithm that may beimplemented for providing feedback regarding a sufficiency of logmessages associated with a change set made to a continuous deliverypipeline in a SaaS environment using the adaptive log system 100described in FIGS. 1-6 using one or more computer systems as definedgenerically in FIG. 9 below, and more specifically by the specificembodiments of FIG. 1.

Embodiments of the method 300 for providing feedback to developers of asufficiency of log messages associated with a change set made to acontinuous delivery pipeline in a SaaS environment, in accordance withembodiments of the present invention, may begin at step 301 wherein acomplexity of the change set made to a pipeline 110 is calculated. Step302 compares a current log message with a previous log message from aprevious run. Step 303 determines a module sensitivity for modules ofthe change set. Step 304 identifies a trust level of the developerassociated with the change set. Step 305 analyzes a serviceability ofthe change set to determine a sufficiency of log messages, for providingfeedback to DevOps.

Referring now to FIG. 8, which depicts a flow chart of a method 400 fordynamically configuring log levels, in accordance with embodiments ofthe present invention. One embodiment of a method 400 or algorithm thatmay be implemented for dynamically configuring log levels using theadaptive log system 100 described in FIGS. 1-6 using one or morecomputer systems as defined generically in FIG. 9 below, and morespecifically by the specific embodiments of FIG. 1.

Embodiments of the method 400 for dynamically configuring log levels, inaccordance with embodiments of the present invention, may begin at step401 wherein a log level is determined for modules of the change set.Step 402 calculates a stability factor of the change set. Step 403applies the stability factor to log level output for change sets. Step404 dynamically configures the log levels to return log messages for aspecific log level.

FIG. 9 depicts a block diagram of a computer system for the adaptive logsystem 100 of FIGS. 1-6, capable of implementing methods for providingfeedback to developers of a sufficiency of log messages associated witha change set made to a continuous delivery pipeline in a SaaSenvironment of FIG. 7, and for dynamically configuring log levels inFIG. 8, in accordance with embodiments of the present invention. Thecomputer system 500 may generally comprise a processor 591, an inputdevice 592 coupled to the processor 591, an output device 593 coupled tothe processor 591, and memory devices 594 and 595 each coupled to theprocessor 591. The input device 592, output device 593 and memorydevices 594, 595 may each be coupled to the processor 591 via a bus.Processor 591 may perform computations and control the functions ofcomputer system 500, including executing instructions included in thecomputer code 597 for the tools and programs capable of implementing amethod for providing feedback to developers of a sufficiency of logmessages associated with a change set made to a continuous deliverypipeline in a SaaS environment, and for dynamically configuring loglevels in the manner prescribed by the embodiments of FIGS. 7-8 usingthe adaptive log system 100 of FIGS. 1-6, wherein the instructions ofthe computer code 597 may be executed by processor 591 via memory device595. The computer code 597 may include software or program instructionsthat may implement one or more algorithms for implementing the methodfor providing feedback to developers of a sufficiency of log messagesassociated with a change set made to a continuous delivery pipeline in aSaaS environment, and for dynamically configuring log levels, asdescribed in detail above. The processor 591 executes the computer code597. Processor 591 may include a single processing unit, or may bedistributed across one or more processing units in one or more locations(e.g., on a client and server).

The memory device 594 may include input data 596. The input data 596includes any inputs required by the computer code 597. The output device593 displays output from the computer code 597. Either or both memorydevices 594 and 595 may be used as a computer usable storage medium (orprogram storage device) having a computer-readable program embodiedtherein and/or having other data stored therein, wherein thecomputer-readable program comprises the computer code 597. Generally, acomputer program product (or, alternatively, an article of manufacture)of the computer system 500 may comprise said computer usable storagemedium (or said program storage device).

Memory devices 594, 595 include any known computer-readable storagemedium, including those described in detail below. In one embodiment,cache memory elements of memory devices 594, 595 may provide temporarystorage of at least some program code (e.g., computer code 597) in orderto reduce the number of times code must be retrieved from bulk storagewhile instructions of the computer code 597 are executed. Moreover,similar to processor 591, memory devices 594, 595 may reside at a singlephysical location, including one or more types of data storage, or bedistributed across a plurality of physical systems in various forms.Further, memory devices 594, 595 can include data distributed across,for example, a local area network (LAN) or a wide area network (WAN).Further, memory devices 594, 595 may include an operating system (notshown) and may include other systems not shown in FIG. 9.

In some embodiments, the computer system 500 may further be coupled toan Input/output (I/O) interface and a computer data storage unit. An I/Ointerface may include any system for exchanging information to or froman input device 592 or output device 593. The input device 592 may be,inter alia, a keyboard, a mouse, etc. or in some embodiments thetouchscreen of a computing device. The output device 593 may be, interalia, a printer, a plotter, a display device (such as a computerscreen), a magnetic tape, a removable hard disk, a floppy disk, etc. Thememory devices 594 and 595 may be, inter alia, a hard disk, a floppydisk, a magnetic tape, an optical storage such as a compact disc (CD) ora digital video disc (DVD), a dynamic random access memory (DRAM), aread-only memory (ROM), etc. The bus may provide a communication linkbetween each of the components in computer 500, and may include any typeof transmission link, including electrical, optical, wireless, etc.

An I/O interface may allow computer system 500 to store information(e.g., data or program instructions such as program code 597) on andretrieve the information from computer data storage unit (not shown).Computer data storage unit includes a known computer-readable storagemedium, which is described below. In one embodiment, computer datastorage unit may be a non-volatile data storage device, such as amagnetic disk drive (i.e., hard disk drive) or an optical disc drive(e.g., a CD-ROM drive which receives a CD-ROM disk). In otherembodiments, the data storage unit may include a knowledge base or datarepository 125 as shown in FIG. 1.

As will be appreciated by one skilled in the art, in a first embodiment,the present invention may be a method; in a second embodiment, thepresent invention may be a system; and in a third embodiment, thepresent invention may be a computer program product. Any of thecomponents of the embodiments of the present invention can be deployed,managed, serviced, etc. by a service provider that offers to deploy orintegrate computing infrastructure with respect to adaptive log messagesystems and methods. Thus, an embodiment of the present inventiondiscloses a process for supporting computer infrastructure, where theprocess includes providing at least one support service for at least oneof integrating, hosting, maintaining and deploying computer-readablecode (e.g., program code 597) in a computer system (e.g., computersystem 500) including one or more processor(s) 591, wherein theprocessor(s) carry out instructions contained in the computer code 597causing the computer system to provide feedback to developers of asufficiency of log messages associated with a change set made to acontinuous delivery pipeline in a SaaS environment, and to dynamicallyconfigure log levels. Another embodiment discloses a process forsupporting computer infrastructure, where the process includesintegrating computer-readable program code into a computer system 500including a processor.

The step of integrating includes storing the program code in acomputer-readable storage device of the computer system 500 through useof the processor. The program code, upon being executed by theprocessor, implements a method for providing feedback to developers of asufficiency of log messages associated with a change set made to acontinuous delivery pipeline in a SaaS environment, and for dynamicallyconfiguring log levels. Thus, the present invention discloses a processfor supporting, deploying and/or integrating computer infrastructure,integrating, hosting, maintaining, and deploying computer-readable codeinto the computer system 500, wherein the code in combination with thecomputer system 500 is capable of performing a method for providingfeedback to developers of a sufficiency of log messages associated witha change set made to a continuous delivery pipeline in a SaaSenvironment, and for dynamically configuring log levels.

A computer program product of the present invention comprises one ormore computer-readable hardware storage devices having computer-readableprogram code stored therein, said program code containing instructionsexecutable by one or more processors of a computer system to implementthe methods of the present invention.

A computer system of the present invention comprises one or moreprocessors, one or more memories, and one or more computer-readablehardware storage devices, said one or more hardware storage devicescontaining program code executable by the one or more processors via theone or more memories to implement the methods of the present invention.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer-readable storagemedium (or media) having computer-readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer-readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer-readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer-readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer-readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer-readable program instructions described herein can bedownloaded to respective computing/processing devices from acomputer-readable storage medium or to an external computer or externalstorage device via a network, for example, the Internet, a local areanetwork, a wide area network and/or a wireless network. The network maycomprise copper transmission cables, optical transmission fibers,wireless transmission, routers, firewalls, switches, gateway computersand/or edge servers. A network adapter card or network interface in eachcomputing/processing device receives computer-readable programinstructions from the network and forwards the computer-readable programinstructions for storage in a computer-readable storage medium withinthe respective computing/processing device.

Computer-readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine-dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer-readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer-readable program instructions by utilizing state information ofthe computer-readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer-readable program instructions.

These computer-readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer-readable program instructionsmay also be stored in a computer-readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that thecomputer-readable storage medium having instructions stored thereincomprises an article of manufacture including instructions whichimplement aspects of the function/act specified in the flowchart and/orblock diagram block or blocks.

The computer-readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce acomputer-implemented process, such that the instructions which executeon the computer, other programmable apparatus, or other device implementthe functions/acts specified in the flowchart and/or block diagram blockor blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

It is to be understood that although this disclosure includes a detaileddescription on cloud computing, implementation of the teachings recitedherein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported, providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure that includes anetwork of interconnected nodes.

Referring now to FIG. 10, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 includes one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A, 54B,54C and 54N shown in FIG. 7 are intended to be illustrative only andthat computing nodes 10 and cloud computing environment 50 cancommunicate with any type of computerized device over any type ofnetwork and/or network addressable connection (e.g., using a webbrowser).

Referring now to FIG. 11, a set of functional abstraction layersprovided by cloud computing environment 50 (see FIG. 10) are shown. Itshould be understood in advance that the components, layers, andfunctions shown in FIG. 11 are intended to be illustrative only andembodiments of the invention are not limited thereto. As depicted, thefollowing layers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may include applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provides pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and adaptive log determination 96.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein

What is claimed is:
 1. A method for providing feedback to developers of a sufficiency of log messages associated with a change set made to a continuous delivery pipeline in a Software as a Service (SaaS) environment, the method comprising: calculating, by a processor of a computing system, a complexity of the change set made to the continuous delivery pipeline in the SaaS environment; comparing, by the processor of the computing system, a current log message created as a result of a test operation of the continuous delivery pipeline in the SaaS environment during a current run with a previous log message created as a result of the test operation of the continuous delivery pipeline in the SaaS environment during a previous run, to determine a log difference between the current log message and the previous log message; determining, by the processor of the computing system, a module sensitivity for each module of the change set; identifying, by the processor of the computing system, a trust level of a developer of the change set; analyzing, by the processor of the computing system, a serviceability of the change set made to the continuous delivery pipeline in the SaaS environment based on: (i) the complexity of the change set, (ii) the log difference between the current log message and the previous log message, (iii) the module sensitivity of each module of the change set, (iv) a stability of changes that were recently introduced in the change set, and (v) the trust level of the developer of the change set, wherein, as a function of the analyzing, the sufficiency of the log messages for each module of the change set is determined; and removing, by the processor of the computing system, the change set from the continuous delivery pipeline in the SaaS environment based on the sufficiency of the log messages for each module of the change set.
 2. The method of claim 1, further comprising: determining, by the processor of the computing system, a log level for each module of the change set based on: (i) the complexity of the change set, (ii) the log difference between the current log message and the previous log message, (iii) the module sensitivity of each module of the change set, and (iv) the trust level of the developer of the change set.
 3. The method of claim 1, wherein a log level determination is further based on a change stability factor, and wherein the change stability factor is calculated over time based on a number of problems occurring with the change set and an effect on an initial log level over time.
 4. The method of claim 3, wherein a log level for each module of the change set is dynamically configured to return log messages of the continuous delivery pipeline in the SaaS environment for a specific log level.
 5. The method of claim 1, wherein calculating the complexity of the change set made to the continuous delivery pipeline in the SaaS environment includes identifying, by the processor of the computing system, modules related to the change set, a developer identification, a type of file that was changed, a kilo of lines of code (KLOC) of the change set, a number of files changed by the change set, a number of work items, and a recency of changes of the change set.
 6. The method of claim 1, wherein determining the module sensitivity for each module of the change set includes: (i) extracting, by the processor of the computing system, information about a defect and a field problem history, a number of developers that contributed to the module, and (ii) calculating, by the processor of the computing system, a module complexity based on a number of files affected by the change set, a size of the files affected by the change set, and a number of cross-references to the files affected by the change set.
 7. The method of claim 1, wherein identifying the trust level of the developer of the change set includes extracting a contribution of the developer of the change set, an experience level of the developer of the change set, and a number of issues reported against the developer of the change set.
 8. A computer system, comprising: a processor; a memory device coupled to the processor; and a computer readable hardware storage device coupled to the processor, wherein the computer readable hardware storage device contains program code executable by the processor via the memory device to implement a method for providing feedback to developers of a sufficiency of log messages associated with a change set made to a continuous delivery pipeline in a Software as a Service (SaaS) environment, the method comprising: calculating, by the processor of the computer system, a complexity of the change set made to the continuous delivery pipeline in the SaaS environment; comparing, by the processor of the computer system, a current log message created as a result of a test operation of the continuous delivery pipeline in the SaaS environment during a current run with a previous log message created as a result of the test operation of the continuous delivery pipeline in the SaaS environment during a previous run, to determine a log difference between the current log message and the previous log message; determining, by the processor of the computer system, a module sensitivity for each module of the change set; identifying, by the processor of the computer system, a trust level of a developer of the change set; analyzing, by the processor of the computer system, a serviceability of the change set made to the continuous delivery pipeline in the SaaS environment based on: (i) the complexity of the change set, (ii) the log difference between the current log message and the previous log message, (iii) the module sensitivity of each module of the change set, (iv) a stability of changes that were recently introduced in the change set, and (v) the trust level of the developer of the change set, wherein, as a function of the analyzing, the sufficiency of the log messages for each module of the change set is determined; and removing, by the processor of the computer system, the change set from the continuous delivery pipeline in the SaaS environment based on the sufficiency of the log messages for each module of the change set.
 9. The computer system of claim 8, further comprising: determining, by the processor of the computing system, a log level for each module of the change set based on: (i) the complexity of the change set, (ii) the log difference between the current log message and the previous log message, (iii) the module sensitivity of each module of the change set, and (iv) the trust level of the developer of the change set.
 10. The computer system of claim 8, wherein a log level determination is further based on a change stability factor, and wherein the change stability factor is calculated over time based on a number of problems occurring with the change set and an effect on an initial log level over time.
 11. The computer system of claim 10, wherein a log level for each module of the change set is dynamically configured to return log messages of the continuous delivery pipeline in the SaaS environment for a specific log level.
 12. The computer system of claim 8, wherein calculating the complexity of the change set made to the continuous delivery pipeline in the SaaS environment includes identifying, by the processor of the computer system, modules related to the change set, a developer identification, a type of file that was changed, a kilo of lines of code (KLOC) of the change set, a number of files changed by the change set, a number of work items, and a recency of changes of the change set.
 13. The computer system of claim 8, wherein determining the module sensitivity for each module of the change set includes: (i) extracting, by the processor of the computing system, information about a defect and a field problem history, a number of developers that contributed to the module, and (ii) calculating, by the processor of the computing system, a module complexity based on a number of files affected by the change set, a size of the files affected by the change set, and a number of cross-references to the files affected by the change set.
 14. The computer system of claim 8, wherein identifying the trust level of the developer of the change set includes extracting a contribution of the developer of the change set, an experience level of the developer of the change set, and a number of issues reported against the developer of the change set.
 15. A computer program product comprising a computer readable hardware storage device storing computer readable program code, the computer readable program code comprising an algorithm that when executed by a processor of a computing system implements a method for providing feedback to developers of a sufficiency of log messages associated with a change set made to a continuous delivery pipeline in a Software as a Service (SaaS) environment, the method comprising: calculating, by the processor of the computing system, a complexity of the change set made to the continuous delivery pipeline in the SaaS environment; comparing, by the processor of the computing system, a current log message created as a result of a test operation of the continuous delivery pipeline in the SaaS environment during a current run with a previous log message created as a result of the test operation of the continuous delivery pipeline in the SaaS environment during a previous run, to determine a log difference between the current log message and the previous log message; determining, by the processor of the computing system, a module sensitivity for each module of the change set; identifying, by the processor of the computing system, a trust level of a developer of the change set; analyzing, by the processor of the computing system, a serviceability of the change set made to the continuous delivery pipeline in the SaaS environment based on: (i) the complexity of the change set, (ii) the log difference between the current log message and the previous log message, (iii) the module sensitivity of each module of the change set, (iv) a stability of changes that were recently introduced in the change set, and (v) the trust level of the developer of the change set, wherein, as a function of the analyzing, the sufficiency of the log messages for each module of the change set is determined; and removing, by the processor of the computing system, the change set from the continuous delivery pipeline in the SaaS environment based on the sufficiency of the log messages for each module of the change set.
 16. The computer program product of claim 15, further comprising: determining, by the processor of the computing system, a log level for each module of the change set based on: (i) the complexity of the change set, (ii) the log difference between the current log message and the previous log message, (iii) the module sensitivity of each module of the change set, and (iv) the trust level of the developer of the change set.
 17. The computer program product of claim 15, wherein a log level determination is further based on a change stability factor, and wherein the change stability factor is calculated over time based on a number of problems occurring with the change set and an effect on an initial log level over time.
 18. The computer program product of claim 17, wherein a log level for each module of the change set is dynamically configured to return log messages of the continuous delivery pipeline in the SaaS environment for a specific log level.
 19. The computer program product of claim 15, wherein calculating the complexity of the change set made to the continuous delivery pipeline in the SaaS environment includes identifying, by the processor of the computing system, modules related to the change set, a developer identification, a type of file that was changed, a kilo of lines of code (KLOC) of the change set, a number of files changed by the change set, a number of work items, and a recency of changes of the change set.
 20. The computer program product of claim 15, wherein determining the module sensitivity for each module of the change set includes: (i) extracting, by the processor of the computing system, information about a defect and a field problem history, a number of developers that contributed to the module, and (ii) calculating, by the processor of the computing system, a module complexity based on a number of files affected by the change set, a size of the files affected by the change set, and a number of cross-references to the files affected by the change set. 